Add a C+Rust library testing job - #346
Merged
Merged
Conversation
--simCodeTarget=C+Rust emits the sources the C target emits and links libSimulationRuntimeRust instead of libSimulationRuntimeC, so a run differs from master in the simulation runtime and nothing else. The job fills c-plus-rust on ryzen-5950x-1, the machine master runs on. The report puts it beside master: report.py diffs every branch against the last one it is given, so `--branches='c-plus-rust master'` makes the per-model tooltips of overview-c-plus-rust.html name the models the two runtimes disagree about, which for this target should be none. The stage passes cmakeFlags, which is what selects the cmake build: libSimulationRuntimeRust is a cmake target with no autotools equivalent, so the autotools build the other C targets use would leave the generated makefile with nothing to link. The testing scripts treat C+Rust as C: -alarm, -abortSlowSimulation, -lv LOG_STATS and the __OpenModelica_simulationFlags annotation. Assisted-by: Claude Opus 5 (1M context)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
--simCodeTarget=C+Rust emits the sources the C target emits and links libSimulationRuntimeRust instead of libSimulationRuntimeC, so a run differs from master in the simulation runtime and nothing else. The job fills c-plus-rust on ryzen-5950x-1, the machine master runs on.
The report puts it beside master: report.py diffs every branch against the last one it is given, so
--branches='c-plus-rust master'makes the per-model tooltips of overview-c-plus-rust.html name the models the two runtimes disagree about, which for this target should be none.The stage passes cmakeFlags, which is what selects the cmake build: libSimulationRuntimeRust is a cmake target with no autotools equivalent, so the autotools build the other C targets use would leave the generated makefile with nothing to link.
The testing scripts treat C+Rust as C: -alarm, -abortSlowSimulation, -lv LOG_STATS and the __OpenModelica_simulationFlags annotation.
Assisted-by: Claude Opus 5 (1M context)